Fix false upgrade notifications when latest Dev Proxy version is already installed #288
+102
−24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR fixes a bug where Dev Proxy Toolkit incorrectly shows upgrade notifications even when the latest version is already installed. The issue occurred because the version extraction logic was picking up version numbers from file paths instead of actual update notifications.
Problem
When
devproxy outdated --shortruns, it can output different things depending on the configuration:When no updates are available:
When an update is available:
The original
extractVersionFromOutputfunction used a generic regex that would match the first version number found, which was always from the file path. This caused false upgrade notifications suggesting users upgrade to the same version they already had installed.Solution
Updated the
extractVersionFromOutputfunction to:/,\, orloaded from)Changes Made
Core Fix
src/detect.ts: EnhancedextractVersionFromOutputfunction with path-aware logicTests Added
Validation
Before & After
Before (❌ Bug):
After (✅ Fixed):
Impact
Users will no longer see misleading upgrade notifications when they already have the latest version. The toolkit now correctly distinguishes between version numbers in file paths versus actual update availability notifications.
Fixes #286.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.